Custom Domain Guide - #45
Merged
Merged
Conversation
Collaborator
Author
NOTE!Making some slight changes to the file so wait till after it's submitted 🪧 |
jasperchess
approved these changes
Aug 14, 2026
jasperchess
approved these changes
Aug 14, 2026
| ### Step 2: Create a CNAME Record | ||
| Add a new CNAME record with the following settings: | ||
| * **Type:** <code>CNAME</code> | ||
| * **Name:** <code>play</code> |
Contributor
There was a problem hiding this comment.
Suggested change
| * **Name:** <code>play</code> | |
| * **Name:** <code>play</code> (creates <code>play.yourdomain.com</code>) |
| Add a new CNAME record with the following settings: | ||
| * **Type:** <code>CNAME</code> | ||
| * **Name:** <code>play</code> | ||
| * **Target:** Your Seedloaf subdomain (do **not** include the port number or `:`) |
Contributor
There was a problem hiding this comment.
Suggested change
| * **Target:** Your Seedloaf subdomain (do **not** include the port number or `:`) | |
| * **Target:** e.g. <code>yoursubdomain.seedloaf.gg</code> (do **not** include the port number or `:`) |
Comment on lines
+15
to
+21
| ### Step 3: Create an SRV Record | ||
| Add a new SRV record with the following details: | ||
| * **Service:** <code>_minecraft</code> | ||
| * **Protocol:** <code>_tcp</code> (some host like cloudflare require you to put the protocol as part of the name field) | ||
| * **Name:** <code>play</code> | ||
| * **Port:** Your Seedloaf port number | ||
| * **Target:** Your new full domain address (e.g., <code>yourdomain.com</code>) |
Contributor
There was a problem hiding this comment.
Suggested change
| ### Step 3: Create an SRV Record | |
| Add a new SRV record with the following details: | |
| * **Service:** <code>_minecraft</code> | |
| * **Protocol:** <code>_tcp</code> (some host like cloudflare require you to put the protocol as part of the name field) | |
| * **Name:** <code>play</code> | |
| * **Port:** Your Seedloaf port number | |
| * **Target:** Your new full domain address (e.g., <code>yourdomain.com</code>) | |
| ### Step 3: Create the SRV Record | |
| Route Minecraft traffic and the custom port to your server: | |
| | Field | Value | Notes | | |
| | :--- | :--- | :--- | | |
| | **Type** | `SRV` | | | |
| | **Service** | `_minecraft` | | | |
| | **Protocol** | `_tcp` (or `TCP`) | | | |
| | **Name / Host** | `play` | Use `@` if you want players to connect using just `yourdomain.com` without `play.` | | |
| | **Priority** | `0` | | | |
| | **Weight** | `0` | | | |
| | **Port** | `[Your Server Port]` | The numeric port assigned in your dashboard | | |
| | **Target** | `play.yourdomain.com` | Must match the CNAME hostname created in Step 2 | | |
| | **TTL** | `Auto` (or `3600`) | | | |
| > **Note for providers with a single "Name" field:** If your registrar does not have separate Service/Protocol fields, enter `_minecraft._tcp.play` in the Name/Host field. |
| * **Target:** Your new full domain address (e.g., <code>yourdomain.com</code>) | ||
|
|
||
| ### Step 4: Done ✅ | ||
| Your custom domain is now linked! Keep in mind that DNS changes may take a few minutes to propagate. Once updated, you can connect to your server using your new domain address! No newline at end of file |
Contributor
There was a problem hiding this comment.
Suggested change
| Your custom domain is now linked! Keep in mind that DNS changes may take a few minutes to propagate. Once updated, you can connect to your server using your new domain address! | |
| Your custom domain is now linked! Keep in mind that DNS changes may take a few minutes to propagate. Once updated, you can connect to your server using your new domain! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the new English (and Spanish) guide for connecting custom domains as requested from Jasper!
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.